PTRACE

Section: System Calls (2)
Index Return to Main Contents

BSD mandoc
NetBSD 1.0BETA

NAME

ptrace - process tracing and debugging

SYNOPSIS

Fd #include <sys/types.h> Fd #include <sys/ptrace.h> Ft int Fn ptrace int request pid_t pid caddr_t addr int data

DESCRIPTION

Fn ptrace provides tracing and debugging facilities. It allows one process (the tracing process) to control another (the traced process). Most of the time, the traced process runs normally, but when it receives a signal Po see sigaction(2) Pc , it stops. The tracing process is expected to notice this via wait(2) or the delivery of a SIGCHLD signal, examine the state of the stopped process, and cause it to terminate or continue as appropriate. Fn ptrace is the mechanism by which all this happens.

The Fa request argument specifies what operation is being performed; the meaning of the rest of the arguments depends on the operation, but except for one special case noted below, all Fn ptrace calls are made by the tracing process, and the Fa pid argument specifies the process ID of the traced process. Fa request can be:

PT_TRACE_ME: This request is the only one used by the traced process; it declares that the process expects to be traced by its parent. All the other arguments are ignored. (If the parent process does not expect to trace the child, it will probably be rather confused by the results; once the traced process stops, it cannot be made to continue except via Eo Fn ptrace Ec .) When a process has used this request and calls execve(2) or any of the routines built on it Po such as execv(3) Pc , it will stop before executing the first instruction of the new image. Also, any setuid or setgid bits on the executable being executed will be ignored.
PT_READ_I , PT_READ_D: These requests read a single int of data from the traced process' address space. Traditionally, Fn ptrace has allowed for machines with distinct address spaces for instruction and data, which is why there are two requests: conceptually, PT_READ_I reads from the instruction space and PT_READ_D reads from the data space. In the current NetBSD implementation, these two requests are completely identical. The Fa addr argument specifies the address (in the traced process' virtual address space) at which the read is to be done. This address does not have to meet any alignment constraints. The value read is returned as the return value from Eo Fn ptrace Ec .
PT_WRITE_I , PT_WRITE_D: These requests parallel PT_READ_I and PT_READ_D except that they write rather than read. The Fa data argument supplies the value to be written.
PT_READ_U: This request reads an int from the traced process' user structure. The Fa addr argument specifies the location of the int relative to the base of the user structure; it will usually be an integer value cast to caddr_t either explicitly or via the presence of a prototype for Eo Fn ptrace Ec . Unlike PT_READ_I and PT_READ_D Fa addr must be aligned on an int boundary. The value read is returned as the return value from Eo Fn ptrace Ec .
PT_WRITE_U: This request writes an int into the traced process' user structure. Fa addr specifies the offset, just as for PT_READ_U and Fa data specifies the value to be written, just as for PT_WRITE_I and PT_WRITE_D
PT_CONTINUE: The traced process continues execution. Fa addr is an address specifying the place where execution is to be resumed (a new value for the program counter), or (caddr_t)1 to indicate that execution is to pick up where it left off. Fa data provides a signal number to be delivered to the traced process as it resumes execution, or 0 if no signal is to be sent.
PT_KILL: The traced process terminates, as if PT_CONTINUE had been used with SIGKILL given as the signal to be delivered.
PT_ATTACH: This request allows a process to gain control of an otherwise unrelated process and begin tracing it. It does not need any cooperation from the to-be-traced process. In this case, Fa pid specifies the process ID of the to-be-traced process, and the other two arguments are ignored. This request requires that the target process must have the same real UID as the tracing process, and that it must not be executing a setuid or setgid executable. (If the tracing process is running as root, these restrictions do not apply.) The tracing process will see the newly-traced process stop and may then control it as if it had been traced all along.
PT_DETACH: This request is like PT_CONTINUE, except that it does not allow specifying an alternate place to continue execution, and after it succeeds, the traced process is no longer traced and continues execution normally.

Additionally, machine-specific requests can exist. On the SPARC, these are:

PT_GETREGS

This request reads the traced process' machine registers into the ``struct reg '' (defined in Aq Pa machine/reg.h ) pointed to by Fa addr .

PT_SETREGS

This request is the converse of PT_GETREGS it loads the traced process' machine registers from the ``struct reg '' (defined in Aq Pa machine/reg.h ) pointed to by Fa addr .

PT_GETFPREGS

This request reads the traced process' floating-point registers into the ``struct fpreg '' (defined in Aq Pa machine/reg.h ) pointed to by Fa addr .

PT_SETFPREGS

This request is the converse of PT_GETFPREGS it loads the traced process' floating-point registers from the ``struct fpreg '' (defined in Aq Pa machine/reg.h ) pointed to by Fa addr .

PT_SYSCALL

This request is like PT_CONTINUE except that the process will stop next time it executes any system call. Information about the system call can be examined with PT_READ_U and potentially modified with PT_WRITE_U through the u_kproc.kp_proc.p_md element of the user structure (see below). If the process is continued with another PT_SYSCALL request, it will stop again on exit from the syscall, at which point the return values can be examined and potentially changed. The u_kproc.kp_proc.p_md element is of type ``struct mdproc '' which should be declared by including Aq Pa sys/param.h , Aq Pa sys/user.h , and Aq Pa machine/proc.h , and contains the following fields (among others):

syscall_num
syscall_nargs
syscall_args[8]
syscall_err
syscall_rv[2]

When a process stops on entry to a syscall, syscall_num holds the number of the syscall, syscall_nargs holds the number of arguments it expects, and syscall_args holds the arguments themselves. (Only the first syscall_nargs elements of syscall_args are guaranteed to be useful.) When a process stops on exit from a syscall, syscall_num is Eo -1 Ec , syscall_err holds the error number Po see errno(2) Pc , or 0 if no error occurred, and syscall_rv holds the return values. (If the syscall returns only one value, only syscall_rv[0] is useful.) The tracing process can modify any of these with PT_WRITE_U only some modifications are useful.

On entry to a syscall, syscall_num can be changed, and the syscall actually performed will correspond to the new number (it is the responsibility of the tracing process to fill in syscall_args appropriately for the new call, but there is no need to modify Eo syscall_nargs Ec ). If the new syscall number is 0, no syscall is actually performed; instead, syscall_err and syscall_rv are passed back to the traced process directly (and therefore should be filled in). If the syscall number is otherwise out of range, a dummy syscall which simply produces an Er ENOSYS error is effectively performed.

On exit from a syscall, only syscall_err and syscall_rv can usefully be changed; they are set to the values returned by the syscall and will be passed back to the traced process by the normal syscall return mechanism.

ERRORS

Some requests can cause Fn ptrace to return -1 as a non-error value; to disambiguate, errno can be set to 0 before the call and checked afterwards. The possible errors are:

Bq Er ESRCH

No process having the specified process ID exists.

Bq Er EINVAL

A process attempted to use PT_ATTACH on itself.
The Fa request was not one of the legal requests.
The Fa addr to PT_READ_U or PT_WRITE_U was not int -aligned.
The signal number (in Fa data ) to PT_CONTINUE or PT_SYSCALL was neither 0 nor a legal signal number.
PT_GETREGS PT_SETREGS PT_GETFPREGS or PT_SETFPREGS was attempted on a process with no valid register set. (This is normally true only of system processes.)

Bq Er EBUSY

PT_ATTACH was attempted on a process that was already being traced.
A request attempted to manipulate a process that was being traced by some process other than the one making the request.
A request (other than PT_ATTACH specified a process that wasn't stopped.

Bq Er EPERM

A request (other than PT_ATTACH attempted to manipulate a process that wasn't being traced at all.
An attempt was made to use PT_ATTACH on a process in violation of the requirements listed under PT_ATTACH above.

BUGS

On the SPARC, the PC is set to the provided PC value for PT_CONTINUE and similar calls, but the NPC is set willy-nilly to 4 greater than the PC value. Using PT_GETREGS and PT_SETREGS to modify the PC, passing (caddr_t)1 to Eo Fn ptrace Ec , should be able to sidestep this.

Single-stepping is not available.

When using PT_SYSCALL there is no easy way to tell whether the traced process stopped because it made a syscall or because a signal was sent at a moment that it just happened to have valid-looking garbage in its ``struct mdproc ''

This document was created by man2html, using the manual pages.
Time: 16:28:59 GMT, April 18, 2022